Please look at a copy of my bcdedit /enum all and let me know if you can see a problem with why my computer will not boot to the recovery environment: Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Windows\system32>bcdedit /enum all Windows Boot Manager -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume2 description Windows Boot Manager locale en-us inherit {globalsettings} default {current} resumeobject {2d1020e0-9b28-11df-a002-a4badbfacbd8} displayorder {current} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.exe description Windows 7 locale en-us inherit {bootloadersettings} recoverysequence {2d1020e2-9b28-11df-a002-a4badbfacbd8} recoveryenabled Yes osdevice partition=C: systemroot \Windows resumeobject {2d1020e0-9b28-11df-a002-a4badbfacbd8} nx OptIn bootstatuspolicy IgnoreShutdownFailures Windows Boot Loader ------------------- identifier {7a17869d-c7c3-11df-92d7-a4badbfacbd8} device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win re.wim,{7a17869e-c7c3-11df-92d7-a4badbfacbd8} path \windows\system32\winload.exe description Windows Recovery Environment inherit {bootloadersettings} osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win re.wim,{7a17869e-c7c3-11df-92d7-a4badbfacbd8} systemroot \windows nx OptIn winpe Yes Resume from Hibernate --------------------- identifier {2d1020e0-9b28-11df-a002-a4badbfacbd8} device partition=C: path \Windows\system32\winresume.exe description Windows Resume Application locale en-US inherit {resumeloadersettings} filedevice partition=C: filepath \hiberfil.sys debugoptionenabled No Windows Memory Tester --------------------- identifier {memdiag} device partition=\Device\HarddiskVolume2 path \boot\memtest.exe description Windows Memory Diagnostic locale en-US inherit {globalsettings} badmemoryaccess Yes EMS Settings ------------ identifier {emssettings} bootems Yes Debugger Settings ----------------- identifier {dbgsettings} debugtype Serial debugport 1 baudrate 115200 RAM Defects ----------- identifier {badmemory} Global Settings --------------- identifier {globalsettings} inherit {dbgsettings} {emssettings} {badmemory} Boot Loader Settings -------------------- identifier {bootloadersettings} inherit {globalsettings} {hypervisorsettings} Hypervisor Settings ------------------- identifier {hypervisorsettings} hypervisordebugtype Serial hypervisordebugport 1 hypervisorbaudrate 115200 Resume Loader Settings ---------------------- identifier {resumeloadersettings} inherit {globalsettings} Device options -------------- identifier {7a17869e-c7c3-11df-92d7-a4badbfacbd8} description Ramdisk Options ramdisksdidevice partition=\Device\HarddiskVolume2 ramdisksdipath \Recovery\WindowsRE\boot.sdi C:\Windows\system32>

Hi, First, you can try Last Known Good Configuration and see if the issue can be fixed. If the issue persists, check if the following suggestions can resolve the issue: 1. Insert the Windows 7 Disc and boot from it. 2. In the recovery menu, choose Command Prompt . 3. Type the following command and press Enter: Chkdsk /r /f 4. Please also try the following commands and press Enter at the end of each line: Ren C:\Windows\winsxs\pending.xml pending.old Ren C:\windows\SoftwareDistribution SDOLD Regedit.exe a. When the register editor opens, please navigate to the following key: HKEY_LOCAL_MACHINE\COMPONENTS b. High light the COMPONENTS key. Please check if the following values exist in the right pane: AdvancedInstallersNeedResolving PendingXmlIdentifier c. If so, please right click on them and choose Delete them. Confirm the operation. d. Restart the computer. 5. try Bootrec: http://support.microsoft.com/kb/927392 Hope this helps. Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.